Created the initial file architecture for the real_estate module,
including the necessary directories and manifest file.

Implemented the estate.property model using Odoo ORM to
define the database table structure required for storing property-related data.

This commit sets up the foundation for the module, making it ready for
further development of features such as property management, views,
and business logic.

Purpose:
Restrict model access and enhance user interaction.

Approach:
Defined access rights via `ir.model.access.csv`; created list, form
and search views with key fields.

Impact:
Users see only permitted records and can easily view, search, and manage
properties through a structured UI.

…uttons

Purpose:
Improve data linkage, automate values, and streamline user actions.

Approach:
- Linked models via One2many, Many2one, and Many2many fields.
- Added computed fields like best_offer and offer_deadline.
- Used onchange for reactive UI updates.
- Added buttons for actions: Sold/Cancel (property), Accept/Refuse (offer).

Impact:
Simplifies workflows, ensures data consistency, and improves overall usability.

…ttons

- Added inline views, statusbar, widget options
- Set SQL & Python constraints for data validity
- Defined default ordering for all models
- Conditional button visibility & field behaviors
- Editable/color-coded list views with decorations
- Stat button for offer count on property type

Purpose:
Introduce a separate module to handle property invoicing and commissions.

Approach:
Created `estate_account` module with billing logic, including fixed admin fees
and percentage-based commissions.

Impact:
Enables optional, reusable invoicing integration for real_estate without
polluting core logic.

Purpose:
Make the code cleaner and more secure.

Approach:
- Renamed methods and variables to follow Odoo naming rules.
- Avoided unsafe public methods and direct field access.

Impact:
Code is easier to read, safer to use, and follows Odoo guidelines.

Purpose:
Control user access, support testing, and improve communication.

Approach:
- Added 'Agent' and 'Manager' groups with role-based access.
- Used groups to control field/button visibility.
- Loaded demo data for testing and training.
- Enabled chatter for tracking messages and changes.

Impact:
Improves security, speeds up development, and adds better collaboration tools.

…ontent

Purpose:
Generate useful reports for properties, offers, and sellers.

Approach:
- Added offer report to property print menu with conditional content.
- Moved offer table to a reusable sub-template.
- Created seller report with related offers.
- Extended property report to include invoice details when sold.

Impact:
Provides clear, flexible reporting for users with reusable templates.

Purpose:
Prevent invalid property sales/offers and fix garden field issues.

Approach:
- Blocked offers on sold properties and sales without accepted offers.
- Fixed garden reset to retain area and orientation when unchecked.

Impact:
Eliminates user confusion and ensures consistent  UI behavior.